Repository navigation
fix(context): preserve message authorship and memory authority - #168
Merged
Merged
Conversation
Bind thread knowledge tools to their project and environment. Add bounded, reversible background memory curation with source and revision validation, project settings, review history, and user-only restoration across clients.
|
Fix the migration ledger, hidden-memory listing, and restore refresh fixtures. Correct Cursor and OpenCode curation test types and record the measured MCP context size. The agent-context-increase maintainer gate remains required.
Preserve human authorship in native-control fixtures, attribute recorded delegation prompts, and assert hidden task memories through the explicit set-aside view. Include the updated memory-isolation base while preserving the PR stack.
Apply curator retirement as automatic forgetting, erase stored history and delivery copies, discard non-standing learning proposals, and clean prior automatic retirements in bounded background batches. Remove set-aside browsing from web and mobile while retaining owner protections and manual supersession controls.
AssistedLearning now discards task and code verdicts before saving, so saveAutomatic no longer takes a verdict or returns "discarded". This also removes the unreachable "unsupported assertion" note, and the test fixtures no longer set a standing-check capability that no client reads. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ation' into fix/agent-message-provenance-wt # Conflicts: # apps/server/src/project/knowledge/AssistedLearning.ts
… names Server code now calls parseNativeGoalCommand and isNativeCompactionCommand directly instead of importing them under the ungated contracts names. Provenance schemas are exported from messageProvenance.ts, and orchestrationV2.ts no longer re-exports them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ScriptedAlchemy
changed the base branch from
fix/project-memory-isolation-curation
to
main
November 19, 2026 19:39
ScriptedAlchemy
enabled auto-merge
November 19, 2026 19:40
isScratchProject resolved symlinks only on the Scratch folder side. A project path under a symlinked directory, such as macOS /var, never matched. Both sides are now resolved before comparing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
T3 persisted sender metadata but dropped it while constructing provider input, summaries and learning evidence. An agent report or system notification could become a human instruction and survive in saved memory. The deeper inspection also reproduced two handoff races: a memory forgotten during context preparation could still be sent from an already-rendered excerpt.
This PR is stacked on #166 (
fix/project-memory-isolation-curation). Its head includes the latest automatic-cleanup base. Merge it into that branch before landing #166 onmain.Changes
Deeper inspection and validation
The legacy-summary attribution gap and both forget races were reproduced with failing regressions before their fixes.
prepared → failed → prepared → sent, with one provider start. Native coverage forgets during pending persistence and verifies that the removed excerpt never reaches injection.vp run check:changed HEAD --concurrency 1 --skip-testscommand ran. Its cached typecheck launcher cannot initialize the workspace's nested seccomp supervisor; the direct focused checks above passed. Behavioral tests ran separately. Local Chromium cannot create its required socket, so the updated browser interaction regression awaits hosted CI.Earlier authored GPT-6 Luna provenance regressions improved agent/notification attribution from 0/9 to 9/9, retained the direct-human summary control at 3/3, and passed 12/12 learning samples. The updated curator prompt in #166 passed 21/21 samples across seven cases. These small samples demonstrate the reproduced cases; they are not a population accuracy estimate, and the final legacy-summary wording was validated deterministically rather than through a new live-model run.
The combined stack advertises a 74,746-byte MCP tool list, 398 bytes above the 74,348-byte main baseline. The existing context-budget workflow is unchanged; this is the same increase as #166, not an additional increase.
Limits
Legacy or external transcripts containing only a
userrole cannot establish whether the original sender was a person or an automated actor. This change preserves and checks provenance where canonical metadata exists, and labels text-only historical summary attribution as unverified. It does not reconstruct sender identity absent from the imported transcript.The explicit-revision recall gate uses conservative pattern matching. Provenance and matching citations establish origin, not truth. Source-backed summaries are revalidated when used; this is not a deployment-wide migration. Original source conversations remain intact, and context a provider has already consumed cannot be unsent. The handoff fix closes the reproduced asynchronous gap before consumption.
This updates code and the PR branch; it does not deploy an environment or rewrite a live database.
Model and harness: GPT-6 Astra Pro in the ChatGPT shared workspace, with delegated implementation and review agents; GPT-6 Luna for the real-model evaluations.